Media identifier generation for camera-captured media

ABSTRACT

A video identifier uniquely identifying a video captured by a camera is generated. The video includes video frames and optionally concurrently captured audio as well as video metadata describing the video. Video data is extracted from at least two of the video&#39;s frames. By combining the extracted video data in an order specified by an identifier generation protocol, an extracted data object is generated. The extracted data object is hashed to generate the unique media identifier, which is stored in association with the video. The identifier generation protocol may indicate the portions of the video data to extract, such as video data corresponding to particular video frames and audio data corresponding to particular audio samples. The extracted data object may include a size of particular video frames, a number of audio samples in the video, or the duration of the video, for example.

BACKGROUND

Field of Art

This application relates in general to capturing and processing videoand in particular to generating unique media identifiers for videoscaptured by a camera.

Description of the Related Art

Modern cameras may store large amounts of media (e.g., video and images)captured by a user. Users typically edit the large amount of capturedinformation to find interesting video portions and images to showfriends. This editing process creates a large number of separate mediafiles derived from the original captured media.

The decreased cost of camera components has increased the number ofusers capturing a scene from multiple viewpoints. For example, someusers employ three-dimensional cameras that capture multipletwo-dimensional images from different image sensors for combination intothree-dimensional media. As another example, some users record a scenefrom distinct cameras, such as a helmet camera, a body camera, and a skitip camera. Each camera or image sensor recording a scene increases thenumber of resulting media files.

Organizing the large number of resulting media files is difficult.Although a media editor could manually navigate through file folders toselect appropriate media, manual navigation is tedious. Such a videostorage paradigm is unfriendly to casual users, who may be discouragedfrom sharing all the interesting moments captured from their camerasbecause they have insufficient time to organize the media files.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosed embodiments have other advantages and features which willbe more readily apparent from the detailed description, the appendedclaims, and the accompanying figures (or drawings). A brief introductionof the figures is below.

Figure (“Fig.” or “FIG.”) 1 illustrates a camera system environment forvideo capture, editing, and viewing, according to one exampleembodiment.

FIG. 2 is a block diagram illustrating a camera system, according to oneexample embodiment.

FIG. 3 is a block diagram of an architecture of a client device (such asa camera docking station or a user device), according to one exampleembodiment.

FIG. 4 is a block diagram of an architecture of a media server,according to one example embodiment.

FIG. 5 is an interaction diagram illustrating processing of a video by acamera docking station and a media server, according to one exampleembodiment.

FIG. 6 is a flowchart illustrating generation of a unique identifier,according to one example embodiment.

FIG. 7 illustrates data extracted from a video to generate a uniquemedia identifier for a video, according to one example embodiment.

FIG. 8 illustrates data extracted from an image to generate a uniquemedia identifier for an image, according to one example embodiment.

FIG. 9 illustrates a set of relationships between videos and videoidentifiers, according to one example embodiment.

DETAILED DESCRIPTION OF THE INVENTION

The figures and the following description relate to preferredembodiments by way of illustration only. It should be noted that fromthe following discussion, alternative embodiments of the structures andmethods disclosed herein will be readily recognized as viablealternatives that may be employed without departing from the principlesof what is claimed.

Reference will now be made in detail to several embodiments, examples ofwhich are illustrated in the accompanying figures. It is noted thatwherever practicable similar or like reference numbers may be used inthe figures and may indicate similar or like functionality. The figuresdepict embodiments of the disclosed system (or method) for purposes ofillustration only. One skilled in the art will readily recognize fromthe following description that alternative embodiments of the structuresand methods illustrated herein may be employed without departing fromthe principles described herein.

Configuration Overview

Embodiments include a method comprising steps for generating a mediaidentifier, a non-transitory computer-readable storage medium storinginstructions that when executed cause a processor to perform steps togenerate a media identifier, and a system for generating a mediaidentifier, where the system comprises the processor and thenon-transitory computer-readable medium.

In one embodiment, a video comprising video frames is accessed. Thevideo is associated with video metadata describing the video. Video datacorresponding to a subset of the video frames is extracted. An extracteddata object is generated. The extracted data objected includes theextracted video data combined with the associated video metadataaccording to an identifier generation protocol. A unique mediaidentifier is generated by hashing the extracted data object. Thegenerated unique media identifier is stored in association with thevideo.

Cloud Environment

FIG. 1 illustrates a camera system environment 100 for video capture,editing, and viewing, according to one example embodiment. Theenvironment includes devices including a camera 110, a docking station120, a media server 130, and a user device 140 communicatively coupledby one or more networks 150. As used herein, either the docking station120 or the user device 140 may be referred to as a “client device.” Inalternative configurations, different and/or additional components maybe included in the camera system environment 100. For example, onedevice functions as both a docking station 120 and a user device 140.Although not shown in FIG. 1, the environment may include a plurality ofany of the devices.

The camera 110 is a device capable of capturing media (e.g., video,images, audio, associated metadata). Media is a digital representationof information, typically aural or visual information. Videos are asequence of image frames and may include audio synchronized to the imageframes. In some embodiments, a still image may be considered as a videowith one image frame. The camera 110 can include a camera body having acamera lens on a surface of the camera body, various indicators on thesurface of the camera body (e.g., LEDs, displays, and the like), variousinput mechanisms (such as buttons, switches, and touch-screenmechanisms), and electronics (e.g., imaging electronics, powerelectronics, metadata sensors) internal to the camera body for capturingimages via the camera lens and/or performing other functions. Asdescribed in greater detail in conjunction with FIG. 2 below, the camera110 can include sensors to capture metadata associated with video data,such as motion data, speed data, acceleration data, altitude data, GPSdata, and the like. A user uses the camera 110 to record or capturemedia in conjunction with associated metadata. The user can edit themedia at a later time. The camera may capture HD (high-definition)video, which may have a large resolution (e.g., 1080 p, 2K, 4K), a highframe rate (e.g., 120 frames per second), or both.

The docking station 120 stores media captured by a camera 110communicatively coupled to the docking station 120 to facilitatehandling of video. For example, the docking station 120 is acamera-specific device for communicatively coupling a camera, forexample, a GOPRO HERO camera, to the media server 130. The camera 110can be coupled to the docking station 120 by wired means (e.g., a USB(universal serial bus) cable, an HDMI (high-definition multimediainterface) cable) or wireless means (e.g., Wi-Fi, Bluetooth, Bluetooth,4G LTE (long term evolution)). The docking station 120 can access videodata and/or metadata from the camera 110, and can transfer the accessedvideo data and/or metadata to the media server 130 via the network 150.For example, the docking station is coupled to the camera 110 through acamera interface (e.g., a communication bus, a connection cable) and iscoupled to the network 150 through a network interface (e.g., a port, anantenna). The docking station 120 retrieves videos and metadataassociated with the videos from the camera via the camera interface andthen uploads the retrieved videos and metadata to the media server 130though the network.

Metadata includes information about the video itself, the camera used tocapture the video, and/or the environment or setting in which a video iscaptured or any other information associated with the capture of thevideo. For example, the metadata is sensor measurements from anaccelerometer or gyroscope communicatively coupled with the camera 110.

Metadata may also include one or more highlight tags, which indicatevideo portions of interest (e.g., a scene of interest, an event ofinterest). Besides indicating a time within a video (or a portion oftime within the video) corresponding to the video portion of interest, ahighlight tag may also indicate a classification of the moment ofinterest (e.g., an event type, an activity type, a scene classificationtype). Video portions of interest may be identified according to ananalysis of quantitative metadata (e.g., speed, acceleration), manuallyidentified (e.g., by a user through a video editor program), or acombination thereof. For example, a camera 110 records a user tagging amoment of interest in a video through recording audio of a particularvoice command, recording one or more images of a gesture command, orreceiving selection through an input interface of the camera 110. Theanalysis may be performed substantially in real-time (during capture) orretrospectively.

The docking station 120 can transcode HD video to LD (lower-definition)video to beneficially reduce the bandwidth consumed by uploading thevideo and to reduce the memory occupied by the video on the media server130. Beside transcoding media to different resolutions, frame rates, orfile formats, the docking station 120 can perform other tasks includinggenerating edited versions of HD videos and generating identifierscorresponding to HD videos. In one embodiment, the docking station 120receives instructions from the media server 130 to transcode and uploadmedia, to generate media identifiers relating to the media, or toperform other tasks on media.

The media server 130 receives and stores videos captured by the camera110 to allow a user to access the videos at a later time. The mediaserver 130 may receive videos via the network 150 from the camera 110 orfrom a client device (e.g., user device 140 or docking station 120). Forinstance, a user may edit an uploaded video, view an uploaded or editedvideo, transfer a video, and the like through the media server 130. Insome embodiments, the media server 130 may provide cloud servicesthrough one or more physical or virtual servers provided by a cloudcomputing service. For example, the media server 130 includesgeographically dispersed servers as part of a content distributionnetwork.

In one embodiment, the media server 130 provides the user with aninterface, such as a web page or native application installed on theuser device 140, to interact with and/or edit the videos captured by theuser. The media server 130 may use the media identifiers to associatethe media with related media to facilitate media editing. For example,the editing interface includes a selection panel with thumbnails of auser's media items. The media items may be grouped based on having incommon any of the media identifiers described herein.

In one embodiment, the media server 130 manages uploads of LD and/or HDvideos from the client device to the media server 130. For example, themedia server 130 allocates bandwidth among client devices uploadingvideos to limit the total bandwidth of data received by the media server130 while equitably sharing upload bandwidth among the client devices.In one embodiment, the media server 130 performs tasks on uploadedvideos. Example tasks include transcoding a video between formats,generating thumbnails for use by a video player, applying edits,extracting and analyzing metadata, and generating media identifiers. Inone embodiment, the media server 130 instructs a client device toperform tasks related to video stored on the client device tobeneficially reduce processing resources used by the media server 130.

A user can experience media and interact with interfaces provided by themedia server 130 via the user device 140. The user device 140 is anycomputing device capable of receiving user inputs as well astransmitting and/or receiving data via the network 150. In oneembodiment, the user device 140 is a conventional computer system, suchas a desktop or a laptop computer. Alternatively, the user device 140may be a device having computer functionality, such as a smartphone, atablet, a mobile telephone, a personal digital assistant (PDA), oranother suitable device. One or more input devices associated with theuser device 140 receive input from the user. For example, the userdevice 140 can include a touch-sensitive display, a keyboard, atrackpad, a mouse, a voice recognition system, and the like.

The user can use the user device 140 to view and interact with or editvideos stored on the media server 130. For example, the user can viewweb pages including video summaries for a set of videos captured by thecamera 110 via a web browser on the user device 140. In someembodiments, the user device 140 may perform one or more functions ofthe docking station 120 such as transcoding HD videos to LD videos anduploading videos to the media server 130.

In one embodiment, the user device 140 executes an application allowinga user of the user device 140 to interact with the media server 130. Forexample, a user can view LD videos stored on the media server 130 andselect highlight moments with the user device 140, and the media server130 generates a video summary from the highlights moments selected bythe user. As another example, the user device 140 can execute a webbrowser configured to allow a user to input video summary properties,which the user device communicates to the media server 130 for storagewith the video. In one embodiment, the user device 140 interacts withthe media server 130 through an application programming interface (API)running on a native operating system of the user device 140, such asIOS® or ANDROID™. While FIG. 1 shows a single user device 140, invarious embodiments, any number of user devices 140 may communicate withthe media server 130.

In one embodiment, the user captures media with the camera 110 andtransfers the media to a docking station 120 or user device 140. Thecamera 110 or a client device communicatively coupled to the cameragenerates a media identifier to uniquely distinguish the media fromother media in the camera system environment 100. The camera 110 orclient device may generate the media identifier in response to capturingthe media, immediately prior to transferring the media, in response toreceiving a copy of the captured media, or in response to storing thecaptured media. The media, or a portion thereof, is transferred to themedia server 130 along with the unique media identifier, and the mediaserver 130 stores the media in association with the unique mediaidentifier. Alternatively or additionally, the media is transferredwithout a unique media identifier, and the media server 130 generatesthe media identifier in response to receiving uploaded media.

In some embodiments, a device (i.e., any device in the camera systemenvironment 100) generates the unique media identifier by hashing anextracted data object formed from data associated with the media in anorder specified by an identifier generation protocol. For a video, theextracted data object includes metadata describing the video as well asvideo data corresponding to a subset of video frames in the video. Foran image, the extracted data object includes metadata describing theimage as well as image data corresponding to pixels in the image.

In some embodiments, the media is associated with additional identifierssuch as an equipment identifier describing equipment used to capture themedia or a shot identifier describing one or more videos captured inphysical proximity during at partially overlapping times. Additionalidentifiers include an occasion identifier describing one more videoscaptured during non-overlapping times within a longer time period (e.g.,a day, a week) and at a particular geographic location (e.g., a beach, amountain, a city). The additional identifiers may be associated withmedia to facilitate organization of the media for editing or sharing.Alternatively or additionally, the additional identifier may be used asmetadata included in the extracted data object hashed to generate aunique media identifier.

When an entity in the media environment generates a derivative versionof media (e.g., by editing, transcoding, or extracting a thumbnail), thederivative version of media is associated with a new unique mediaidentifier generated from the derivative version. The unique mediaidentifier of the parent media from which the derivative version wasgenerated is also associated with the derivative version. Because thederivative version of the media (also referred to as child media)typically has at least a different start frame or a different end framefrom the parent media, the child media typically contains a subset offrames from the parent media. Because the unique media identifierdepends on the frames of the video, the child media has a unique mediaidentifier different from the unique media identifier of the parentmedia. In some embodiments, the unique media identifier depends on aduration value in a video's metadata, so child media clipped from parentmedia will have a different unique identifier due at least to thechanged duration. Even if the child media includes frames derived fromall the frames of the parent media, the child media still has adifferent unique media identifier because the child media typicallyincludes altered frames due to application of transcoding (e.g.,compression, format changes), image processing effects (e.g., colorshifts, contrast enhancements, brightness adjustments), or videoprocessing effects (e.g., playback speed modifications, audiofiltering).

The camera 110, the docking station 120, the media server 130, and theuser device 140 communicate with each other via the network 150, whichmay include any combination of local area and/or wide area networks,using both wired (e.g., T1, optical, cable, DSL) and/or wirelesscommunication systems (e.g., WiFi, mobile). In one embodiment, thenetwork 150 uses standard communications technologies and/or protocols.In some embodiments, all or some of the communication links of thenetwork 150 may be encrypted using any suitable technique or techniques.It should be noted that in some embodiments, the media server 130 islocated within the camera 110 itself.

Example Camera Configuration

FIG. 2 is a block diagram illustrating a camera system, according to oneembodiment. The camera 110 includes one or more microcontrollers 202(such as microprocessors) that control the operation and functionalityof the camera 110. A lens and focus controller 206 is configured tocontrol the operation and configuration of the camera lens. A systemmemory 204 is configured to store executable computer instructions that,when executed by the microcontroller 202, perform the camerafunctionalities described herein. It is noted that the microcontroller202 is a processing unit and may be augmented with or substituted by aprocessor. A synchronization interface 208 is configured to synchronizethe camera 110 with other cameras or with other external devices, suchas a remote control, a second camera 110, a camera docking station 120,a smartphone or other user device 140, or a media server 130.

A controller hub 230 transmits and receives information from various I/Ocomponents. In one embodiment, the controller hub 230 interfaces withLED lights 236, a display 232, buttons 234, microphones such asmicrophones 222 a and 222 b, speakers, and the like.

A sensor controller 220 receives image or video input from an imagesensor 212. The sensor controller 220 receives audio inputs from one ormore microphones, such as microphone 222 a and microphone 222 b. Thesensor controller 220 may be coupled to one or more metadata sensors 224such as an accelerometer, a gyroscope, a magnetometer, a globalpositioning system (GPS) sensor, or an altimeter, for example. Ametadata sensor 224 collects data measuring the environment and aspectin which the video is captured. For example, the metadata sensorsinclude an accelerometer, which collects motion data, comprisingvelocity and/or acceleration vectors representative of motion of thecamera 110; a gyroscope, which provides orientation data describing theorientation of the camera 110; a GPS sensor, which provides GPScoordinates identifying the location of the camera 110; and analtimeter, which measures the altitude of the camera 110.

The metadata sensors 224 are coupled within, onto, or proximate to thecamera 110 such that any motion, orientation, or change in locationexperienced by the camera 110 is also experienced by the metadatasensors 224. The sensor controller 220 synchronizes the various types ofdata received from the various sensors connected to the sensorcontroller 220. For example, the sensor controller 220 associates a timestamp representing when the data was captured by each sensor. Thus,using the time stamp, the measurements received from the metadatasensors 224 are correlated with the corresponding video frames capturedby the image sensor 212. In one embodiment, the sensor controller beginscollecting metadata from the metadata sources when the camera 110 beginsrecording a video. In one embodiment, the sensor controller 220 or themicrocontroller 202 performs operations on the received metadata togenerate additional metadata information. For example, themicrocontroller 202 may integrate the received acceleration data todetermine the velocity profile of the camera 110 during the recording ofa video.

Additional components connected to the microcontroller 202 include anI/O port interface 238 and an expansion pack interface 240. The I/O portinterface 238 may facilitate the receiving or transmitting video oraudio information through an I/O port. Examples of I/O ports orinterfaces include USB ports, HDMI ports, Ethernet ports, audioports,and the like. Furthermore, embodiments of the I/O port interface 238 mayinclude wireless ports that can accommodate wireless connections.Examples of wireless ports include Bluetooth, Wireless USB, Near FieldCommunication (NFC), and the like. The expansion pack interface 240 isconfigured to interface with camera add-ons and removable expansionpacks, such as a display module, an extra battery module, a wirelessmodule, and the like.

Example Client Device Architecture

FIG. 3 is a block diagram of an architecture of a client device (such asa camera docking station 120 or a user device 140), according to oneembodiment. The client device includes a processor 310 and a memory 330.Conventional components, such as power sources (e.g., batteries, poweradapters) and network interfaces (e.g., micro USB port, an Ethernetport, a Wi-Fi antenna, or a Bluetooth antenna, supporting electroniccircuitry), are not shown to so as to not obscure the details of thesystem architecture.

The processor 310 includes one or more computational nodes, such as acentral processing unit (CPU), a core of a multi-core CPU, a graphicsprocessing unit (GPU), a microcontroller, an application-specificintegrated circuit (ASIC), a field programmable gate array (FPGA), orother processing device such as a microcontroller or state machine. Thememory 330 includes one or more computer-readable media, includingnon-volatile memory (e.g., flash memory), and volatile memory (e.g.,dynamic random access memory (DRAM)).

The memory 330 stores instructions (e.g., computer program code)executable by the processor 310 to provide the client devicefunctionality described herein. The memory 330 includes instructions formodules. The modules in FIG. 3 include a video uploader 350, a videoediting interface 360, and a task agent 370. In other embodiments, themedia server 130 may include additional, fewer, or different componentsfor performing the functionalities described herein. For example, thevideo editing interface 360 is omitted when the client device is adocking station 120. As another example, the client device includesmultiple task agents 370. Conventional components, such as input/outputmodules to manage communication with the network 150 or the camera 110,are not shown.

Also illustrated in FIG. 3 is a local storage 340, which may be adatabase and/or file system of memory 330. The local storage 340 storesvideos, images, and recordings transferred from a camera 110 as well asassociated metadata. In one embodiment, a camera 110 is paired with theclient device through a network interface (e.g., a port, an antenna) ofthe client device. Upon pairing, the camera 110 sends media storedthereon to the client device (e.g., through a Bluetooth or USBconnection), and the client device stores the media in the local storage340. For example, the camera 110 can transfer 64 GB of media to theclient device in a few minutes. In some embodiments, the client deviceidentifies media captured by the camera 110 since a recent transfer ofmedia from the camera 110 to the client device 120. Thus, the clientdevice can transfer media without manual intervention by a user. Themedia may then be uploaded to the media server 130 in whole or in part.For example, an HD video is uploaded to the media server 130 when theuser elects to post the video to a social media platform. The localstorage 340 can also store modified copies of media. For example, thelocal storage 340 includes LD videos transcoded from HD videos capturedby the camera 110. As another example, the local storage 340 stores anedited version of an HD video.

The video uploader 350 sends media from the client device to the mediaserver 130. In some embodiments, in response to the HD video beingtransferred to the client device from a camera and transcoded by thedevice, a unique media identifier is generated for the transcoded LDvideo. The transcoded LD video is automatically uploaded to the mediaserver 130. Alternatively or additionally, a user can manually select LDvideo to upload to the media server 130. The uploaded LD video can beassociated with an account of the user, for instance allowing a user toaccess the uploaded LD video via a cloud media server portal, such as awebsite.

In one embodiment, the media server 130 controls the video uploader 350.For example, the media server 130 determines which videos are uploaded,the priority order of uploading the videos, and the upload bitrate. Theuploaded media can be HD videos from the camera 110, transcoded LDvideos, or edited portions of videos. In some embodiments, the mediaserver 130 instructs the video uploader 350 to send videos to anotherclient device. For example, a user on vacation transfers HD videos fromthe user's camera 110 to a smart phone user device 140, which the mediaserver 130 instructs to send the HD videos to the user's docking station120 at home while the smart phone user device 140 has Wi-Fi connectivityto the network 150. Video uploading is described further in conjunctionwith FIGS. 4 and 5.

The video editing interface 360 allows a user to browse media and editthe media. The client device can retrieve the media from local storage340 or from the media server 130. For example, the user browses LDvideos retrieved from the media server on a smart phone user device 140.In one embodiment, the user edits an LD video to reduce processingresources when generating previews of the modified video. In oneembodiment, the video editing interface 360 applies edits to an LDversion of a video for display to the user and generates an edit tasklist to apply the edits to an HD version of the video. The edit decisionlist encodes a series of flags (or sequencing files) that describe tasksto generate the edited video. For example, the edit decision listidentifies portions of video and the types of edits performed on theidentified portions.

Editing a video can include specifying video sequences, scenes, orportions of the video (“portions” collectively herein), indicating anorder of the identified video portions, applying one or more effects toone or more of the portions (e.g., a blur effect, a filter effect, achange in frame rate to create a time-lapse or slow motion effect, anyother suitable video editing effect), selecting one or more soundeffects to play with the video portions (e.g., a song or other audiotrack, a volume level of audio), or applying any other suitable editingeffect. Although editing is described herein as performed by a user ofthe client device, editing can also be performed automatically (e.g., bya video editing algorithm or template at the media server 130) ormanually by a video editor (such as an editor-for-hire associated withthe media server 130). In some embodiments, the editor-for-hire mayaccess the video only if the user who captured the video configures anappropriate access permission.

The task agent 370 obtains task instructions to perform tasks (e.g., tomodify media and/or to process metadata associated with the media). Thetask agent 370 can perform tasks under the direction of the media server130 or can perform tasks requested by a user of the client device (e.g.,through the video editing interface 360). The client device can includemultiple task agents 370 to perform multiple tasks simultaneously (e.g.,using multiple processing nodes) or a single task agent 370. The taskagent 370 also includes one or more modules to perform tasks. Thesemodules include a thumbnail generator 372, an edit conformer 373, ametadata extractor 374, and an identifier generator 376. The task agent370 may include additional modules to perform additional tasks, may omitmodules, or may include a different configuration of modules.

The thumbnail generator 372 obtains thumbnail instructions and outputs athumbnail, which is an image generated from a portion of a video. Athumbnail refers to an image extracted from a source video. Thethumbnail may be at the same resolution as the source video or may havea different resolution (e.g., a low-resolution preview thumbnail). Thethumbnail may be generated directly from a frame of the video orinterpolated between successive frames of a video. The thumbnailinstructions identify the source video and the one or more frames of thevideo to generate the thumbnail, and other properties of the thumbnail(e.g., file format, resolution). The thumbnail instructions may begenerated by a user (e.g., through a frame capture command on the videoediting interface 360) or automatically (e.g., to generate a previewthumbnail of the video in a video viewing interface). The thumbnailgenerator 372 may generate a low-resolution thumbnail, or the thumbnailgenerator 372 may retrieve an HD version of the video to generate ahigh-resolution thumbnail. For example, while previewing an LD versionof the video on a smart phone user device 140, a user selects a frame ofa video to email to a friend, and the thumbnail generator 372 prepares ahigh-resolution thumbnail to insert in the email. In the example, themedia server 130 instructs the user's docking station 120 to generatethe high-resolution thumbnail from a locally stored HD version of thevideo and to send the high-resolution frame to the smart phone userdevice 140.

In response to generation of a thumbnail from a video, the videoidentifier generator 376 creates a unique media identifier for thethumbnail, which is stored in association with the thumbnail.Additionally, the thumbnail is stored in association with the uniquemedia identifier of the video from which the thumbnail was generated.

The edit conformer 373 obtains an edit decision list (e.g., from thevideo editing interface 360) and generates an edited video based on theedit decision list. The edit conformer 373 retrieves the portions of theHD video identified by the edit decision list and performs the specifiededit tasks. For instance, an edit decision list identifies three videoportions, specifies a playback speed for each, and identifies an imageprocessing effect for each. As another example, the edit decision listincludes transcoding instructions to apply to a video or a portion ofthe video. Transcoding instructions identify the portion of media to betranscoded and properties of the transcoded video (e.g., file format,resolution, frame rate). To process the example edit decision list, theedit conformer 373 of the client device storing the HD video accessesthe identified three video portions, edits each by implementing thecorresponding specified playback speed, applies the correspondingidentified image processing effect, and combines the edited portions tocreate an edited HD video.

In response to generating the edited version of a video, the identifiergenerator 376 generates a media identifier based on the edited versionof the video. The edited version of the video may be stored as aseparate video from the original video, or the edited version mayoverride the original video. In either case, the edited video isassociated with the parent media identifier of the original video.

The metadata extractor 374 obtains metadata instructions and outputsanalyzed metadata based on the metadata instructions. Metadata includesinformation about the video itself, the camera 110 used to capture thevideo, or the environment or setting in which a video is captured or anyother information associated with the capture of the video. Examples ofmetadata include: telemetry data (such as motion data, velocity data,and acceleration data) captured by sensors on the camera 110; locationinformation captured by a GPS receiver of the camera 110; compassheading information; altitude information of the camera 110; biometricdata such as the heart rate of the user, breathing of the user, eyemovement of the user, body movement of the user, and the like; vehicledata such as the velocity or acceleration of the vehicle, the brakepressure of the vehicle, or the rotations per minute (RPM) of thevehicle engine; or environment data such as the weather informationassociated with the capture of the video. Metadata may also includeidentifiers associated with media (described in further detail inconjunction with the identifier generator 376) and user-supplieddescriptions of media (e.g., title, caption).

Metadata instructions identify a video, a portion of the video, and themetadata task. Metadata tasks include generating condensed metadata fromraw metadata samples in a video. Condensed metadata may summarizemetadata samples temporally or spatially. To obtain the condensedmetadata, the metadata extractor 374 groups metadata samples along oneor more temporal or spatial dimensions into temporal and/or spatialintervals. The intervals may be consecutive or non-consecutive (e.g.,overlapping intervals representing data within a threshold of a time ofa metadata sample). From an interval, the metadata extractor 374 outputsone or more pieces of condensed metadata summarizing the metadata in theinterval (e.g., using an average or other measure of central tendency,using standard deviation or another measure of variance). The condensedmetadata summarizes metadata samples along one or more differentdimensions than the one or more dimensions used to group the metadatainto intervals. For example, the metadata extractor performs a movingaverage on metadata samples in overlapping time intervals to generatecondensed metadata having a reduced sampling rate (e.g., lower datasize) and reduced noise characteristics. As another example, themetadata extractor 374 groups metadata samples according to spatialzones (e.g., different segments of a ski run) and outputs condensedmetadata representing metadata within the spatial zones (e.g., averagespeed and acceleration within each spatial zone).

The metadata extractor 374 may perform other metadata tasks such asidentifying highlights or events in videos from metadata for use invideo editing (e.g., automatic creation of video summaries). Forexample, metadata can include acceleration data representative of theacceleration of a camera 110 attached to a user as the user captures avideo while snowboarding down a mountain. Such acceleration metadatahelps identify events representing a sudden change in accelerationduring the capture of the video, such as a crash or landing from a jump.Generally, the metadata extractor 374 may identify highlights or eventsof interest from an extremum in metadata (e.g., a local minimum, a localmaximum) or a comparison of metadata to a threshold metadata value. Themetadata extractor 374 may also identify highlights from processedmetadata such as derivative of metadata (e.g., a first or secondderivative) an integral of metadata, smoothed metadata (e.g., a movingaverage, a local curve fit or spline), or a combination thereof. Asanother example, a user may audibly “tag” a highlight moment by saying acue word or phrase while capturing a video. The metadata extractor 374may subsequently analyze the sound from a video to identify instances ofthe cue phrase and to identify portions of the video recorded within athreshold time of an identified instance of the cue phrase.

In another metadata task, the metadata extractor 374 analyzes thecontent of a video to generate metadata. For example, the metadataextractor 374 takes as input video captured by the camera 110 in avariable bit rate mode and generates metadata describing the bit rate.Using the metadata generated from the video, the metadata extractor 374may identify potential scenes or events of interest. For example,high-bit rate portions of video can correspond to portions of videorepresentative of high amounts of action within the video, which in turncan be determined to be video portions of interest to a user. Themetadata extractor 374 identifies such high-bit rate portions for use bya video creation algorithm in the automated creation of an edited videowith little to no user input. Thus, metadata associated with capturedvideo can be used to identify best scenes in a video recorded by a userwith fewer processing steps than used by image processing techniques andwith more user convenience than manual curation by a user.

The metadata extractor 374 may obtain metadata directly from the camera110 (e.g., the metadata is transferred along with video from thecamera), from a user device 140 (such as a mobile phone, computer, orvehicle system associated with the capture of video), an external sensorpaired with the camera 110 or user device 140, or from external metadatasources 110 such as web pages, blogs, databases, social networkingsites, servers, or devices storing information associated with the user(e.g., a fitness device recording activity levels and user biometrics).

The identifier generator 376 obtains identifier instructions to generatean identifier for media and associates the generated identifier with themedia. The identifier instructions identify the media to be identifiedby the unique identifier and may identify any relationships of the mediato other media items, equipment used to capture the media item, andother context related to capturing the media item. In some embodiments,the identifier generator 376 registers generated identifiers with themedia server 130, which verifies that an identifier is unique (e.g., ifan identifier is generated based at least in part on pseudo-randomnumbers). In other embodiments, the identifier generator 376 isimplemented within the media server 130 and maintains a register ofissued identifiers to avoid associating media with a duplicateidentifier used by an unrelated media item.

In some embodiments, the identifier generator 376 generates unique mediaidentifiers for a media item based on the content of the media andmetadata associated with the media. For example, the identifiergenerator 376 selects portions of a media item and/or portions ofmetadata and then hashes the selected portions to output a unique mediaidentifier.

In some embodiments, the identifier generator 376 associates media withunique media identifiers of related media. In one embodiment, theidentifier generator associates a child media item derived from a parentmedia item with the unique media identifier of the parent media item.This parent unique media identifier (i.e., the media identifiergenerated based on the parent media) indicates the relationship betweenthe child media and the parent media. For example, if a thumbnail imageis generated from a video image, the thumbnail image is associated with(a) a unique media identifier generated based at least in part on thecontent of the thumbnail image and (b) a parent unique media identifiergenerated based at least in part on the content of the parent video.Grandchild media derived from child media of an original media file maybe associated with the unique media identifiers of the original mediafile (e.g., a grandparent unique media identifier) and the child media(e.g., a parent unique media identifier). Generation of unique mediaidentifiers is described further with respect to FIGS. 6-9.

In some embodiments, the identifier generator 376 associates media withan equipment identifier describing equipment used to capture the mediaand associates the media with the obtained equipment identifier.Equipment identifiers include a device identifier of the camera used tocapture the media. For example, a camera's serial number is the deviceidentifier associated with media captured by the camera. Deviceidentifiers also include sensor identifiers (e.g., serial numbers) ofmetadata sensors communicatively coupled to the camera. For example,media captured by a skier includes device identifiers for the camera anda sensor identifier of communicatively coupled metadata sensor such asan altimeter, accelerometer, or thermometer. Alternatively oradditionally, media captured by the example camera is associated with acompound device identifier indicating the camera-metadata sensorcombination. Compound device identifiers may be formed by hashing orconcatenating the camera identifier and sensor identifier.

Equipment identifiers also include a rig identifier of a camera rig,which is a group of cameras (e.g., camera 110) that records multiplefields of view from the camera rig. For example, a camera rig includesleft and right cameras to capture three-dimensional video, or cameras tocapture three-hundred-sixty-degree video, or cameras to capturespherical video. In some embodiments, the rig identifier is a serialnumber of the camera rig, or is based on the device identifiers ofcameras in the camera rig (e.g., through concatenating or hashing of thedevice identifiers). A camera rig may include multiple image sensors(each associated with a camera identifier) housed in a single housing ormultiple cameras 110 mechanically coupled, communicatively coupled, orboth by a modular connector.

Equipment identifiers may include camera group identifiers. A cameragroup identifier identifies one or more cameras 110 and/or camera rigsin physical proximity and used to record multiple perspectives in one ormore shots. For example, two chase skydivers each have a camera 110, anda lead skydiver has a spherical camera rig. In this example, mediacaptured by the cameras 110 of the spherical camera rig have the samerig identifier, and all the media captured by the chase skydivers andlead skydivers has the same camera group identifier. Camera groupidentifiers may be generated from an arrangement (e.g., concatenation)or manipulation (e.g., hash) of the device identifiers (or portionsthereof) of the constituent cameras 110 and/or camera rigs, a start orend time associated with the camera group, a random identifier, or acombination thereof.

In one embodiment, the identifier generator 376 associates videos with acommon camera group identifier by determining that the cameras 110 thatcaptured the videos are part of common camera group. For example, theidentifier generator 376 groups cameras 110 into a camera group inresponse to metadata describing positions of the cameras 110 anddetermines that the cameras 110 are part of a camera group in responseto the cameras 110 being within a threshold distance (e.g., 1 meter, 3meters, 10 meters, 30 meters, 100 meters) at a common time.Alternatively or additionally, the identifier generator 376 groupscameras 110 into a camera group in response to metadata indicating thatcameras were communicatively coupled (e.g., via Bluetooth) at a commontime or under control by a master device controlling capture, such as amaster camera 110 included in the cameras or a separate client device.The identifier generator 376 assigns a camera group identifier to thecameras 110 in the camera group. The identifier generator 376 thenassociates videos captured at the common time (i.e., having the commontime between each video's start timestamp and end timestamp) with thecamera group identifier assigned to the camera group.

In some embodiments, the identifier generator 376 generates contextidentifiers based at least in part on device unique identifiers and/orrig unique identifiers of devices and/or camera rigs in the cameragroup. The identifier generator 376 obtains a context identifierdescribing context in which the media was captured and associates themedia with the context identifier. Obtaining a context identifierincludes generating a context identifier or accessing a previouslygenerated context identifier.

Context identifiers include shot identifiers, which correspond to videoscaptured at least partially at overlapping times by a camera group aspart of a “shot.” For example, each time a camera group begins asynchronized capture, the identifier generator 376 determines that mediaresulting from the synchronized capture are part of a shot. Thus, videosrecorded by a camera group during a production session may have a commoncamera group identifier but different shot identifiers corresponding todifferent shots during the production session. In response toidentifying media as part of a shot, the identifier generator 376associates the media captured by the have a same shot identifier. Insome embodiments, the shot identifier is based at least in part on ahash of the time a shot begins, the time a shot ends, the geographicallocation of the shot, and/or one or more equipment identifiers of cameraequipment used to capture a shot.

In some embodiments, a video editor segments videos having a common shotidentifier into multiple temporal portions (e.g., each corresponding toan event of interest). The resulting videos derived from portions of theinitial videos may each be associated with an additional shot identifierto indicate which videos correspond to a common temporal portion. Forexample, a camera group of four cameras captures 4 videos from a commontime period 10 minutes in duration, and an editor identifies threedistinct events of interests occurring between 1-2 minutes, 5-6 minutes,and 8-9 minutes from the start of the shot. In the example, the editresults in twelve videos, where there are four videos (one for eachcamera) corresponding to each event of interest. The identifiergenerator 376 associates the four videos corresponding to each event ofinterest with an additional shot identifier for that portion in additionto (or in place of) a shot identifier corresponding to the initial 10minutes for the initial 4 uncut videos.

Context identifiers also include occasion identifiers, which indicatemedia captured as part of several shots during an occasion. Videoshaving a common occasion may encompass multiple video shots. Occasionsmay be identified from videos shot in a common time range. Alternativelyor additionally, videos having a common occasion may also be identifiedbased at least in part on a common geographical location (e.g., shotswithin a threshold radius of a geographical coordinate), a commonsubject matter, or both. Occasions may be defined by a user curatingmedia, or the identifier generator 376 may cluster media into occasionsbased on associated time of capture, geographical location, or othermetadata associated with media. Example occasions encompass shots takenduring a day skiing champagne powder, shots taken during a multi-dayhiking trek, or shots taken during a family trip to an amusement park.In some embodiments, an occasion identifier is based at least in part ona user description of an occasion or on a hash of a time, location, userdescription, or shot identifier of a shot included in the occasion.

Example Media Server Architecture

FIG. 4 is a block diagram of an architecture of a media server 130,according to one embodiment. The media server 130 includes a user store410, a video store 420, an upload manager 430, a task agent 440, a videoediting interface 460, and a web server 470. In other embodiments, themedia server 130 may include additional, fewer, or different componentsfor performing the functionalities described herein. For example, thetask agent 470 is omitted. Conventional components such as networkinterfaces, security functions, load balancers, failover servers,management and network operations consoles, and the like are not shownso as to not obscure the details of the system architecture.

Each user of the media server 130 creates a user account, and useraccount information is stored in the user store 410. A user accountincludes information provided by the user (such as biographicinformation, geographic information, and the like) and may also includeadditional information inferred by the media server 130 (such asinformation associated with a user's previous use of a camera). Examplesof user information include a username, a first and last name, contactinformation, a user's hometown or geographic region, other locationinformation associated with the user, and the like. The user store 410may include data describing interactions between a user and videoscaptured by the user. For example, a user account can include a uniqueidentifier associating videos uploaded by the user with the user's useraccount.

The media store 420 stores media captured and uploaded by users of themedia server 130. The media server 130 may access videos captured usingthe camera 110 and store the videos in the media store 420. In oneexample, the media server 130 may provide the user with an interfaceexecuting on the user device 140 that the user may use to upload videosto the video store 315. In one embodiment, the media server 130 indexesvideos retrieved from the camera 110 or the user device 140, and storesinformation associated with the indexed videos in the video store. Forexample, the media server 130 provides the user with an interface toselect one or more index filters used to index videos. Examples of indexfilters include but are not limited to: the type of equipment used bythe user (e.g., ski equipment, snowboard equipment, mountain bikeequipment, scuba diving equipment, etc.), the type of activity beingperformed by the user while the video was captured (e.g., skiing,snowboarding, mountain biking, scuba diving, etc.), the time and data atwhich the video was captured, or the type of camera 110 used by theuser.

In some embodiments, the media server 130 generates a unique identifierfor each video stored in the media store 420. In some embodiments, thegenerated identifier for a particular video is unique to a particularuser. For example, each user can be associated with a first uniqueidentifier (such as a 10-digit alphanumeric string), and each videocaptured by a user is associated with a second unique identifier made upof the first unique identifier associated with the user concatenatedwith a video identifier (such as the unique media identifier describedwith respect to the identifier generator 376 and FIGS. 6-9). Thus, eachvideo identifier is unique among all videos stored at the media store420, and can be used to identify the user that captured the video.

The metadata store 425 stores metadata associated with videos stored bythe media store 420. For instance, the media server 130 can retrievemetadata from the camera 110, the user device 140, or one or moremetadata sources 110. The metadata store 425 may include one or moreidentifiers associated with media (e.g., unique media identifier, deviceidentifier, equipment identifier, shot identifier, occasion identifier).The metadata store 425 can store any type of metadata, including but notlimited to the types of metadata described herein. It should be notedthat in some embodiments, metadata corresponding to a video is storedwithin a video file itself, and not in a separate storage.

The upload manager 430 obtains an upload policy and instructs clientdevices to upload media based on the upload policy. The upload policyindicates which media may be uploaded to the media server 130 and how toprioritize among a user's media as well as how to prioritize amonguploads from different client devices. The upload manager 430 obtainsregistration of media available in the local storage 340 but notuploaded to the media server 130. For example, the client deviceregisters HD videos when transferred from a camera 110 and registers LDvideos upon completion of transcoding from HD videos. The upload manager430 selects media for uploading to the media server 130 from among theregistered media based on the upload policy. For example, the uploadmanager 430 instructs client devices to upload LD videos and edited HDvideos but not raw HD videos.

The media server 130 may include one or more task agents 440 to provideone or more of the functionalities described above with respect to thetask agents 370 or FIG. 3. Task agents 440 included in the media server130 may provide different functionality (e.g., a different subset of thefunctionalities described with respect to modules 372, 373, 374, 376)from task agents 370 included in the client device.

The media server 130 may include a video editing interface 460 toprovide one or more of the editing functionalities described above withrespect to the video editing interface 360 of FIG. 3. The video editinginterface 360 provided by the media server 130 may differ from the videoediting interface 360 provided by a client device. For example,different client devices have different video editing interfaces 360 (inthe form of native applications) that provide different functionalitiesdue to different display sizes and different input means. As anotherexample, the media server 130 provides the video editing interface 460as a web page or browser application accessed by client devices.

The web server 470 provides a communicative interface between the mediaserver 130 and other entities of the environment of FIG. 1. For example,the web server 470 can access videos and associated metadata from thecamera 110 or a client device to store in the media store 420 and themetadata store 425, respectively. The web server 470 can also receiveuser input provided to the user device 140 and can request videos storedon a user's client device when the user request's the video from anotherclient device.

Uploading Media

FIG. 5 is an interaction diagram illustrating processing of a video by acamera docking station and a media server, according to one embodiment.Different embodiments may include additional or fewer steps in differentorder than that described herein.

A client device registers 505 with the media server 130. Registering 505a client device includes associating the client device with one or moreuser accounts, but some embodiments may provide for uploading a videowithout creating a user account or with a temporary user account.Registering the media may include transmitting a unique media identifiergenerated for the video. The client device subsequently connects 510 toa camera 110 (e.g., through a dedicated docking port, through Wi-Fi orBluetooth). As part of connecting 510, media stored on the camera 110 istransferred to the client device, and may be stored 520 locally (e.g.,in local storage 340). For example, the client device requests the videousing the unique media identifier, and the camera 110 retrieves thevideo using the unique media identifier and transfers the video inresponse to the request. The client device registers 515 the video withthe media server 130. Registering the video may include transmitting theunique media identifier, which may be generated by the camera 110 or theclient device, and the video's file size. For example, the media server130 creates a unique entry in the video store 420 that include thevideo's unique media identifier and file size. Alternatively oradditionally, a video is registered with the media server 130 using atemporary identifier, and the media server 130 generates a unique mediaidentifier and sends the unique media identifier to the client deviceand/or camera 110 for association with the video.

The client device may send a device status report to the media server130 as part registering 515 a video, registering the client device, orany subsequent communication with the media server 130. The devicereport may include quantitative metrics, qualitative metrics, and/oralerts describing client device resources (e.g., memory resources,processing resources, power resources, connectivity resources).

Generating Unique Media Identifiers

FIG. 6 is a flowchart illustrating generation of a unique identifier,according to one embodiment. Different embodiments may includeadditional or fewer steps in different order than that described herein.In some embodiments, the identifier generator 376 on a client device (ormedia server 130) provides the functionality described herein.

The identifier generator 376 obtains media (e.g., a video or an image).For example, the media is obtained from local storage 340, or portionsof the media are transferred via the network. The identifier generator376 extracts 620 video data and/or extracts 630 image data from themedia, as described in further detail with respect to FIGS. 7 and 8,respectively.

Turning to FIG. 7, it illustrates example data extracted 620 from avideo to generate a unique media identifier for a video, according toone embodiment. In the example illustrated in FIG. 7, the video is anMP4 or LRV (low-resolution video) file. Extracted video data includesdata related to time such as the creation time 701 of the media (e.g.,beginning of capture, end of capture), duration 702 of the video, andtimescale 703 (e.g., seconds, minutes) of the duration 702. For example,the identifier generator 376 accesses, from the video metadata, aduration value indicating a time duration of the video and a timescalevalue corresponding to a timescale of the duration value. The identifiergenerator 376 generates the extracted data object comprising theextracted video data combined with the duration value and the timescalevalue in an order specified by the identifier generation protocol.

Other extracted video data includes size data, such as total size, firstframe size 704, size of a subsequent frame 705 (e.g., 300), size of thelast frame 706, number of audio samples 707 in a particular audio track,and total number of audio samples, mdat atom size 708. (The mdat atomrefers to the portion of an MP4 file that contains the video content.)To extract the size data (e.g., 704, 705, 706), the identifier generator376 accesses a video frame having a frame number specified by theidentifier generation protocol. The identifier generator 376 determinesan amount of image data in the accessed video frame and combines thetruncated image data with other extracted video data in an orderspecified by the identifier generation protocol. For example, the videoidentifier generator 376 accesses a video frame atom comprising all thevideo's video frames and one or more hierarchically nested headers toorganize the video frame. The video identifier generator 376 determinesa number of atom bits in the accessed video frame atom and generates theextracted data object by combining the determined number of atom bitswith other data in an order specified by the identifier generationprotocol.

Other extracted video data includes video content such as first framedata 709, particular frame (e.g., 300) data 710, last frame data 711,and audio data 712 from a particular track. To extract the video content(e.g., 709, 710, 711), the identifier generator 376 accesses a videoframe having a frame number specified by the identifier generationprotocol. For example, the identifier generation protocol species thefirst frame, last frame, and a frame at a particular index (e.g., the 42^(nd) frame). The identifier generator 376 may determine whether toaccess data from a frame at a particular index in response todetermining that the number of video frames in the video exceeds theparticular index. The identifier generator 376 may truncate image datain the access video frame to a predetermined number of bits specified bythe identifier generation protocol. The identifier generator 376combines the access (and optionally truncated) image data into theextracted video data in an order specified by the identifier generationprotocol.

To extract audio content (e.g., 712), the identifier generator 376accesses a channel of the audio or a portion of the audio (e.g., a timerange) specified by the identifier generation protocol and combines theaudio data from the specified channel and/or portion with other data inan order specified by the identifier generation protocol. The identifiergenerator 376 may optionally determine a number of audio samples (oraudio data size such as number of bits) in the accessed video data andcombine the determine number of audio samples (or audio data size) withother video data in an order specified by the identifier generationprotocol. In some embodiments, the identifier generator 376 includes thenumber of audio samples (or audio size data) in the extracted video datain response to determining that the accessed audio includes a number ofaudio samples (or duration of audio) equaling or exceeding a thresholdnumber of audio samples (or audio duration).

Other extracted video data includes user data, device data, or any othermetadata associated with the video, which may be contained in udta atomdata 713, for example. The udta atom refers to the portion of an MP4file that contains user-specified or device-specified data. Theidentifier generator 376 may extract metadata associated with the videosuch as a video duration, video capture time, video capture date, videoresolution, video frame rate, user identifier, or a user-specifiedcaption. In some embodiments, the identifier generator 376 selects themetadata for inclusion by truncating the metadata (e.g., udta atom data713) to less than a threshold size (e.g., 32 bytes). The identifiergenerator 376 combines extracted metadata with other video data in anorder specified by the identifier generation protocol.

In some embodiments, the identifier 376 associates videos with anotheridentifier such as an equipment identifier (e.g., camera identifier,sensor identifier, camera rig identifier, camera group identifier), ashot identifier, an occasion identifier, a parent media identifier.However, associating a video with another identifier does not modify theunique media identifier of the video. In other words, these otheridentifiers are not included in the extracted data object used todetermine the unique media identifier. Similarly, associating a videowith a highlight tag or chapter break marker does not modify the video'sunique media identifier, and highlight tags and chapter breaks are notincluded in the extracted data object used to determine the unique mediaidentifier.

Turning to FIG. 8, it illustrates data extracted 630 (shown in FIG. 6)from an image to generate a unique media identifier for an image (e.g.,a still image, a video frame), according to on embodiment. In theexample illustrated in FIG. 8, the image is a JPEG file. Extracted imagedata includes image size data 801. For example, the image size data 801is the number of bytes of image content between the start of scan (SOS,located at marker 0xFFDA in a JPEG file) and the end of image (EOI,located at marker 0xFFD9 in a JPEG file). The image size data may referto the size of data in the original image or in a compressed version ofan image. Extracted image data includes user-provided data such as animage description 802 or maker note 803. The user-provided data may begenerated by a device (e.g., a file name). Extracted image data mayinclude image content 804, which the identifier generator 376 may accessand truncate according to a threshold amount of data (e.g., 5 kilobytes)specified by the identifier generator. The identifier generator 376combined the image data, image metadata, or data derived therefrom in anorder specified by the identifier generation protocol.

Data extracted 620, 630 from media may also include geographicallocation (e.g., of image capture), an indicator of file format type, aninstance number (e.g., different transcodes of a media file havedifferent instance numbers), a country code (e.g., of devicemanufacture, of media capture), and/or an organization code.

Turning back to FIG. 6, the identifier generator 376 generates anextracted data object comprising the extracted data arranged in an orderspecified by the identifier generation protocol. The data in theextracted data object is suitable for hashing, and may be converted tobinary or any other suitable format for compatibility with the hashfunction. To generate 376 the unique media identifier, the identifiergenerator 376 hashes the extracted data object. For example, the hashfunction is the CityHash to output 128 bits, beneficially reducingchances of duplicate unique media identifiers among unrelated mediaitems. However, any hash function outputting any number of bits may beused. As used herein, a “hash” or “hash function” refers to adeterministic algorithm that transforms input data into output data withthe size of the output data (e.g., 256 bits, 128 bits, 64 bits)typically being less than the size of the input data. In someembodiments, the unique media identifier is the output of the hashfunction. In other embodiments, the output of the hash function iscombined with a header (e.g., index bytes to indicate that theidentifier's type is unique media identifier, a unique identifier of theuser who captured or otherwise causes the media to be created).

The generated unique media identifier is output 660. The unique mediaidentifier is stored as metadata in association with the input media.For example, the video is modified to include the media identifier byincorporating the media identifier into a header of the video.Alternatively or additionally, the video is modified to include themedia identifier by encoding the unique media identifier as a watermarkin the audio or video frames of the video. The device that generates themedia identifier may communicate the identifier to other entities in thecamera system environment to ensure consistent, efficient identificationof the media. In some embodiments, an edited version of the media isassociated with a new unique media identifier generated based on theedited version of the media.

The process described with respect to FIGS. 6 and 7 may be used togenerate a unique media identifier for an audio file even if the audiodoes not accompany a video or still image. For example, the identifiergenerator omits extracting data describing video frames but does extract620 data such as creation time 701, duration 702, timescale 703, numberof audio samples 707, mdat atom size 708, audio content 712, udta atomdata 713, or a combination thereof.

Similarly, the identifier generator 376 may generate a unique identifierfor an image using the extracted data described with respect to FIG. 8,or with a subset of the extracted data described with respect to FIG. 7.The identifier generator 376 extracts 620 data as if the still imagewere a one frame video. For example, the extracted data does not includedata related to an intermediate frame (e.g., 705, 710) and audio (e.g.,707, 712). Data related to the last frame (e.g., 706, 711) may beomitted, or the data extracted 620 from the first frame (i.e., theimage) may be duplicated as data extracted 620 from the last frame.

In some embodiments, the media server 130 uses the generated uniquemedia identifier to identify the media in a video viewing interface. Forexample, the media server sends previews of a video along with thevideo's unique media identifier to a client device. After a user selectsthe preview of the video through the video viewing interface, the clientdevice requests the video using the unique media identifier. In responseto receiving the request with the unique media identifier, the mediaserver 130 retrieves the video (or a version thereof such as alow-definition version) from the video store 420 using the unique mediaidentifier and transmits the video to the requesting client device.

As another example, a user edits a low-resolution version of a videothrough an editing interface presented by a client device while ahigher-resolution version video is stored remotely from the clientdevice. An edit decision list describing edits selected by the user withthe client device are sent along with the unique media identifier of thevideo to the storage device storing the higher-resolution version (e.g.,docking station 120, media server 130). The storage device retrieves thehigher-resolution version of the video using the unique mediaidentifier, and generates an edited version of the retrieved videoaccording to the transmitted edit decision list. The edited version maybe associated with the unique media identifier of the higher-resolutionversion, a new unique media identifier generated based on the editedversion, or both.

Media Identifier Relationships

FIG. 9 illustrates a set of relationships between videos and videoidentifiers (such as the video identifiers created by the camera systemor transcoding device), according to an embodiment. In a firstembodiment, a video is associated with a first unique identifier. Aportion of the video (for instance, a portion selected by the user) isassociated with a second unique identifier, and is also associated withthe first identifier Similarly, a low-resolution version of the video isassociated with a third identifier, and is also associated with thefirst identifier.

Video data from each of two different videos can be associated with thesame event. For instance, each video can capture an event from adifferent angle. Each video can be associated with a differentidentifier, and both videos can be associated with the same eventidentifier. Likewise, a video portion from a first video and a videoportion from a second video can be combined into the edited videosequence. The first video can be associated with an identifier, and thesecond video can be associated with a different identifier, and bothvideos can be associated with an identifier associated with the videosequence.

In some embodiments, multiple parent media correspond to a child mediaitem. For example, two or more videos are consolidated to form aspherical, three-dimensional (3D), panoramic, or wide angle video. Theinitial videos (each captured from a separate camera or image sensor)may be associated with a unique media identifier. When consolidated intoa spherical, 3D, or panoramic video (e.g., by stitching overlappingfields of view together), the resulting video has its own child mediaidentifier. However, the consolidated video is also associated withparent media identifiers of the files used to generate the consolidatedvideo.

In some embodiments, the identifier generator 376 generates a uniquemedia identifier for a burst media file, which is a plurality of imagescaptured within a short (e.g., one second) period of time. Each of theimages may have a unique media identifier determined as described withrespect to FIG. 8. To determine an overall unique media identifier forthe burst media file, the identifier generator 376 assembles the imagesof the burst media file in chronological order and then generates theunique media identifier for the resulting video. As another example, theidentifier generator 376 determines a unique identifier for a time lapsevideo (i.e., a series of images captured over an interval such as one,five, or minutes or hours) in a similar manner to generating the uniqueidentifier for a burst video.

The identifier generator 376 may generate a unique media identifier fora chaptered video, which may include separate video files correspondingto each chapter. A unique media identifier is determined for each videocorresponding to a chapter. The videos corresponding to chapters may beassembled into an overall video in an order specified by the video'seditor, and the identifier generator 376 may generate another uniqueidentifier for this overall video.

Additional Configuration Considerations

The disclosed embodiments beneficially facilitate management of videofiles. Generating identifiers indicating multiple characteristics of avideo facilitates retrieving a set of videos having a samecharacteristic (and accordingly one matching identifier). The set ofvideos may then displayed to a user to facilitate editing or used togenerate a consolidated video or edited video. A consolidated video(e.g., 3D, wide-angle, panoramic, spherical) comprises video datagenerated from multiple videos captured from different perspectives(often from different cameras of a camera rig). For example, whenmultiple cameras or camera rigs capture different perspectives on ashot, the shot identifier facilitates retrieval of videos correspondingto each perspective for use in editing a video. As another example, acamera rig identifier, combined with timestamp metadata, provides formatching of videos from the different cameras of the camera rig tofacilitate creation of consolidated videos. The disclosed embodimentsbeneficially reduce processing time and increase efficiency ofgenerating a unique media identifier by hashing an extracted subset ofdata from the video or image rather than hashing the entire video.Hashing the subset of data is orders of magnitude faster than hashingall the data in an image or video.

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms, for example, as illustrated inFIGS. 3 and 4. Modules may constitute software modules (e.g., codeembodied on a machine-readable medium or in a transmission signal),hardware modules, or a combination thereof. A hardware module istangible unit capable of performing certain operations and may beconfigured or arranged in a certain manner. In example embodiments, oneor more computer systems (e.g., a standalone, client or server computersystem) or one or more hardware modules of a computer system (e.g., aprocessor or a group of processors) may be configured by software (e.g.,an application or application portion) as a hardware module thatoperates to perform certain operations as described herein.

The performance of certain of the operations may be distributed amongthe one or more processors, not only residing within a single machine,but deployed across a number of machines. In some embodiments, the oneor more processors or processor-implemented modules may be located in asingle geographic location (e.g., within a home environment, an officeenvironment, or a server farm). In other example embodiments, the one ormore processors or processor-implemented modules may be distributedacross a number of geographic locations.

Unless specifically stated otherwise, discussions herein using wordssuch as “processing,” “computing,” “calculating,” “determining,”“presenting,” “displaying,” or the like may refer to actions orprocesses of a machine (e.g., a computer) that manipulates or transformsdata represented as physical (e.g., electronic, magnetic, or optical)quantities within one or more memories (e.g., volatile memory,non-volatile memory, or a combination thereof), registers, or othermachine components that receive, store, transmit, or displayinformation.

Some embodiments may be described using the expression “coupled” and“connected” along with their derivatives. For example, some embodimentsmay be described using the term “coupled” to indicate that two or moreelements are in direct physical or electrical contact. The term“coupled,” however, may also mean that two or more elements are not indirect contact with each other, but yet still co-operate or interactwith each other. The embodiments are not limited in this context.Further, unless expressly stated to the contrary, “or” refers to aninclusive or and not to an exclusive or.

Upon reading this disclosure, those of skill in the art will appreciatestill additional alternative structural and functional designs for asystem and a process for video identifier generation. Thus, whileparticular embodiments and applications have been illustrated anddescribed, it is to be understood that the disclosed embodiments are notlimited to the precise construction and components disclosed herein.Various apparent modifications, changes and variations may be made inthe arrangement, operation and details of the method and apparatusdisclosed herein without departing from the spirit and scope defined inthe appended claims.

What is claimed is:
 1. A system for generating unique identifiers, thesystem comprising: one or more physical processors configured bymachine-readable instructions to: access a media item, the media itemincluding an image, a video, or an audio; access an identifiergeneration protocol, the identifier generation protocol specifying anorder in which to arrange data extracted from the media item; extractfirst data and second data from the media item; generate an extracteddata object by combining the first data and the second data, the firstdata and the second data arranged in the order specified by theidentifier generation protocol; obtain a unique media identifier for themedia item by hashing the extracted data object; and store the uniquemedia identifier.
 2. The system of claim 1, wherein the first dataincludes information related to an image portion of the media item, anaudio portion of the media item, a capture of the media item, or a userof the media item.
 3. The system of claim 2, wherein the informationrelated to the image portion of the media item includes a size, an imageportion, or a resolution of one or more video frames in the media item.4. The system of claim 3, wherein the one or more video frames includenon-consecutive video frames.
 5. The system of claim 2, wherein theinformation related to the audio portion of the media item includes asize or a number of audio samples in the media item.
 6. The system ofclaim 2, wherein the identifier generation protocol specifies one ormore audio channels of the media item from which the information relatedto the audio portion of the media item is extracted.
 7. The system ofclaim 2, wherein the information related to the capture of the mediaitem includes a duration of the media item, a timescale of the duration,a time of capture, a rate of capture, a format of capture, a location ofcapture, or a device identifier of a device that captured the mediaitem.
 8. The system of claim 2, wherein the information related to theuser of the media item includes a user identifier or a user-specifieddescription for the media item.
 9. The system of claim 1, wherein theone or more physical processors are, to store the unique mediaidentifier, further configured by the machine-readable instruction tomodify the media item to include the unique media identifier.
 10. Thesystem of claim 8, wherein the unique media identifier is included inthe media item as a watermark.
 11. The system of claim 1, wherein theone or more physical processors are, to store the unique mediaidentifier, further configured by the machine-readable instruction togenerate metadata associated with the media item.
 12. The system ofclaim 1, wherein the one or more physical processors are, to extract thefirst data and the second data from the media item, further configuredby the machine-readable instruction to truncate one or both of the firstdata and the second data to a predetermined number of bits specified bythe identifier generation protocol.
 13. The system of claim 1, whereinthe identifier generation protocol specifies the first data and thesecond data to be extracted from the media item.
 14. The system of claim1, wherein the first data and the second data are of same data type. 15.The system of claim 1, wherein the first data and the second data are ofdifferent data types.
 16. A method for generating unique identifiers,the method performed by a computing system including one or morephysical processors, the method comprising: accessing, by the computingsystem, a media item, the media item including an image, a video, or anaudio; accessing, by the computing system, an identifier generationprotocol, the identifier generation protocol specifying an order inwhich to arrange data extracted from the media item; extracting, by thecomputing system, first data and second data from the media item;generating, by the computing system, an extracted data object bycombining the first data and the second data, the first data and thesecond data arranged in the order specified by the identifier generationprotocol; obtaining, by the computing system, a unique media identifierfor the media item by hashing the extracted data object; and storing, bythe computing system, the unique media identifier.
 17. The method ofclaim 16, wherein the first data includes information related to animage portion of the media item, an audio portion of the media item, acapture of the media item, or a user of the media item.
 18. The methodof claim 16, wherein the identifier generation protocol specifies thefirst data and the second data to be extracted from the media item. 19.The method of claim 16, wherein extracting the first data and the seconddata from the media item includes truncating one or both of the firstdata and the second data to a predetermined number of bits specified bythe identifier generation protocol.
 20. The method of claim 16, whereinstoring the unique media identifier includes modifying the media item toinclude the unique media identifier.